Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Kubernetes and Tekton in dependencies and documentation #1397

Merged

Conversation

SaschaSchwarze0
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 commented Oct 9, 2023

Changes

I am changing the supported Kubernetes versions to 1.25 to 1.28. The CI will run 1.25 and 1.28.

I am changing the supported Tekton versions to 0.47 and 0.50 which are LTS versions. The CI will run 0.47.

I am updating the go.mod dependencies to Tekton 0.47 which itself has Kubernetes dependencies set to 1.26 which I have therefore consistently set in go.mod as well.

Generated files are updates.

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

Release Notes

The supported Kubernetes releases are now 1.25 to 1.28. The supported Tekton versions are 0.47 and 0.50

@SaschaSchwarze0 SaschaSchwarze0 added the kind/dependency-change Categorizes issue or PR as related to changing dependencies label Oct 9, 2023
@openshift-ci openshift-ci bot added the release-note Label for when a PR has specified a release note label Oct 9, 2023
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.12.0 milestone Oct 9, 2023
@openshift-ci openshift-ci bot requested a review from otaviof October 9, 2023 14:46
@SaschaSchwarze0 SaschaSchwarze0 changed the title Sascha update k8s tekton Update Kubernetes and Tekton in dependencies and documentation Oct 9, 2023
@SaschaSchwarze0 SaschaSchwarze0 removed the request for review from otaviof October 9, 2023 14:53
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-update-k8s-tekton branch 3 times, most recently from 8aafe02 to e9e229c Compare October 9, 2023 15:08
Copy link
Contributor

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you! looks neat

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed lgtm Indicates that a PR is ready to be merged. labels Oct 10, 2023
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-update-k8s-tekton branch 2 times, most recently from 0d53736 to 74cb2c1 Compare October 11, 2023 18:58
@qu1queee
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 11, 2023
@openshift-ci openshift-ci bot merged commit 6acc965 into shipwright-io:main Oct 11, 2023
11 checks passed
@SaschaSchwarze0 SaschaSchwarze0 deleted the sascha-update-k8s-tekton branch August 7, 2024 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/dependency-change Categorizes issue or PR as related to changing dependencies lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants